home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
china306.zip
/
CHINA.DOC
< prev
next >
Wrap
Text File
|
1992-02-13
|
7KB
|
201 lines
China Sea Trader
Release 3.0
February 13th 1992
Written by - Roland Haley
Rural Route #7 Woodstock
Ontario N4S 7W2 Canada
HALEY'S COMMENT BULLETIN BOARD
USRobotics HST 9600-baud
(519) 469-3028
(519) 469-3173
(519) 539-6851
DOOR Setup
Make a batch file to run the DOOR as described in your PCBoard
(R) documentation.
Example:
CD \DOORS
CHINA CHINA.CFG <== Runs CHINA.EXE passing a parameter of CHINA.CFG
CD \PCB An example of this file is below.
BOARD
Example CHINA.CFG file:
C:\PCB\PCBOARD.SYS <== The location of this file
Haley's Comment BBS <== The name of your BBS
Roland <== The SysOps FIRST name
Haley <== The SysOps LAST name
0 <== Registration number
Environment Variables
Two environment variables must be set in your AUTOEXEC.BAT file:
SET LIB=<drive:><path to DORPCH33.EXE> Note: ONLY the PATH !
Example: SET LIB=C:\MYLIB
The DORPCH33.EXE run-time library must then be placed in this
directory. If you keep the library in the <current directory>
with the DOOR program then this environment variable is NOT
required. I would suggest a separate directory - perhaps a
RAMDISK as I do on my system.
SET DOORPCH=PCB This variable tells DORPCH33.EXE it is
running on a PCBoard system
All DOORPCH 3.3 DOORS require the DORPCH33.EXE run-time library
and the Microsoft (R) QuickBASIC 3.0 run-time library,
BRUN30.EXE, be present. Your DOOR program may have come with
these files in the ARC file. If they are not present, this DOOR
program WILL NOT RUN. You should contact the DOOR author if the
files are missing. You require one and only one version of these
two libraries for ALL DOORPCH 3.3 DOORware. The files are also
available in DORPCH33.ARC available on most PCBoard Bulletin
Board Systems. If you wish a fully detailed explanation of how
DOORPCH operates with DOORS, then you may read the documentation
within the DORPCH33.ARC file within which this documentation may
be found.
DOOR Operation
When the DOOR is in operation you have complete control over the
caller. This DOOR was written using DOORPCH version 3.3. The
logic is safe. However, if something goes wrong - like real bad
wrong, sorry but we probably can't help. Every precaution has
been taken to insure this code works flawlessly. If it doesn't,
let us know. Many function/operational keys are at your
disposal/use:
F1 - Displays the version of DOORPCH compiled and linked
into the DOOR.
F2 - Displays a callers Alias if one is used via the Door
Monitor program (DOORPCH version) - future.
F3 - Reserved for the future.
F4 - Toggles the Bell on/off. May activate the DOOR Bell.
Value is returned to PCBoard when DOOR completes.
F5 - DOS Shell. Allows SysOp to exit to DOS from inside a
DOOR.
F6 - Displays available MEMORY and available STRING space.
F7 - Toggle the alarm on/off. May activate the DOOR Alarm.
Value is returned to PCBoard when DOOR completes.
F8 - Returns the caller involuntarily to PCBoard.
F9 - Toggles the display on/off.
Value is returned to PCBoard when DOOR completes.
F10 - Activates SysOp / Caller CHAT mode within the DOOR.
ESC - Deactivates CHAT mode. DOOR is resumed.
HOME - HELP key for line 24/25 capabilities.
END - Displays Callers name and miscellaneous information.
PG-DN- Displays Data Phone, Home Phone, Security Level
Uploads, Downloads and Expiration Date.
PG-UP- Displays Comments from the callers USER record.
UP - Allows the SysOp to temporarily add additional time
to the caller while in the DOOR. This time is NOT
returned to the BBS.
DN - Allows the SysOp to temporarily subtract time from the
caller while in the DOOR. This time is NOT returned
to the BBS.
ALT-N - SysOp next on control/indicator.
Value is returned to PCBoard when DOOR completes.
ALT-X - PCBoard will exit after current caller completes their
session. Value is returned to PCBoard when DOOR
completes.
If you are running in NON-GRAPHICS mode, you MUST have ANSI.SYS
installed as a device driver in your CONFIG.SYS file:
Example: DEVICE=ANSI.SYS
DOORPCH uses this device driver for displaying all colors to the
local console. Color Graphics will always be sent to the local
console if you have defined to PCBSetup that you are running
graphics on the local monitor. If a caller is in non-graphics
mode (NG) on line 25, you will still see colors if PCBSetup has
been configured that way. The reverse is also true. If the
caller is in graphics mode (GR) on line 25) and the local console
is defined to be in non-graphics mode then colors will NOT be
displayed to the local console.
BELL
DOORPCH logic will not allow a BELL to be sent to the local
console when the local screen is inactive (F9 OFF).
ERRORS
All errors should recover and cause the DOOR program to exit
gracefully and return to the main system. All errors are logged
in the "DOORPCH.ERR" file. The error number and line number are
included with the date and time. Errors will be either caused by
the main module (the authors code, contact him) or the doorpch
sub (contact DOORPCH people). It should NEVER cause the board to
hang. If your board hangs, you are obligated to contact the
appropriate party and report the error and circumstances that
caused it. Because we are using Microsoft's (c) QuickBASIC 3.0
run-time routines, it is possible that basic will detect a fatal
error condition. As mentioned above, we have taken every
precaution, but simply cannot code for every error condition.
The Door should run without error.
If you are running this door on your system, and find it to be
entertaining. Please register your copy by sending $20 to:
HALEY'S COMMENT BBS
R.R.#7
Woodstock, Ontario
Canada N4S 7W2
Include the exact display name of your BBS for your registration
number to place in the CHINA.CFG file. The door program will then
run with the enhancements.